Back

Chapter 6 of the content provided focuses on various aspects of careers, including surviving as an older worker in the tech world, the ideal length of job tenure, strategies for hiring and team building, and performance management systems.

The first article, titled “Surviving as an Old in the Tech World” from Wired, discusses the challenges faced by older workers in the tech industry. It emphasizes the importance of continuously learning and evolving to remain relevant in such a rapidly changing field. The article suggests that experience and wisdom can be valuable assets, but older workers must also actively embrace new technologies and adapt their skills.

The second article, published on the Wealthfront blog, explores the question of how long one should stay at a job. It argues that staying at a job for too short a period can hinder career growth, while staying for too long may lead to stagnation. The article advises that ideal job tenure should be around two to four years, as this allows for enough time to learn and contribute while also showcasing the ability to adapt and take on new challenges.

The third link provides information about Will Larson, an experienced engineering leader and author. His LinkedIn profile highlights his work at various companies, including Digg, Uber, and Stripe. Larson’s profile serves as a resource for learning about his career in engineering leadership and his insights on hiring, team building, and performance management.

The fourth link leads to Rands in Repose, a blog written by Michael Lopp (also known as Rands). The post titled “Wanted” discusses the qualities that Lopp looks for in potential team members. He emphasizes the importance of hiring people who are driven, curious, and possess good judgment. Lopp also stresses the need for diversity in teams and the value of problem-solving skills.

The fifth article, from Comparably’s blog, lists the best places to work based on a competition held by the company. The competition includes categories such as Best Company Culture, Best CEOs, and Best Companies for Women. The article provides insights into the companies that were recognized for their exceptional work environments.

The next two links lead to Lever and Greenhouse, both of which are talent acquisition platforms. These platforms help companies streamline their hiring processes, from sourcing candidates to managing the interview and offer stages. These tools enable companies to build diverse and effective teams.

In the eighth link, the author of the website Lethain offers a “membership opportunity” to those interested in receiving exclusive content, including articles and in-depth analysis of various engineering topics.

The ninth link is a duplicate of the eighth link, leading to the same “membership opportunity” mentioned above.

Link ten leads to a blog post by Julia Evans discussing her year in review for 2017. She highlights her accomplishments, challenges, and the technical topics she explored throughout the year.

The eleventh link, titled “First Team,” is another post from Lethain. It explains the importance of developing a cohesive and high-performing first engineering team and provides insights into the hiring and team-building process.

The twelfth link directs readers to an article on Business Insider that criticizes the practice of stack ranking employees. The article argues that this method of employee evaluation, popularized by companies like Microsoft, can be demoralizing and counterproductive.

The thirteenth link leads to a book called “Work Rules!: Insights from Inside Google That Will Transform How You Live and Lead” by Laszlo Bock, former Senior Vice President of People Operations at Google. The book offers insights into Google’s unique approach to talent management and leadership.

The fourteenth link takes readers to an article by Lethain discussing the concept of “skewing” and the challenges faced by frontend engineers. The article explains how project skew—a mismatch between an engineer’s skill level and the complexity of the work assigned—can lead to dissatisfaction and reduced productivity.

In the fifteenth link, the author of Lethain provides a comprehensive guide to implementing an effective hiring funnel. The article outlines the stages of the funnel, including sourcing, screening, and interviewing, and offers tips and best practices for each step.

The sixteenth link leads to another Lethain article detailing the design and implementation of performance management systems. The article discusses the challenges of performance evaluation, suggests different approaches, and highlights the importance of feedback and career development.

Link seventeen directs readers to the Wikipedia page on Site Reliability Engineering (SRE). SRE is a discipline that combines operational expertise and software engineering to ensure the reliability and availability of large-scale systems.

The eighteenth link leads to an article by Lethain discussing the complexities and considerations involved in running an engineering reorganization within a company. The article offers insights into communication, decision-making, and organizational design.

The nineteenth link is another article by Lethain, this time exploring the concept of career levels and their role in professional growth and development. The article discusses the challenges and benefits of career leveling frameworks and offers suggestions for implementing effective leveling structures.

The twentieth link brings readers back to the Lethain article on performance management systems mentioned earlier.

In the twenty-first link, once again, readers are directed to the Lethain article on the hiring funnel.

Link twenty-two leads to the Amazon page for the book “Cracking the Coding Interview” by Gayle Laakmann McDowell. The book provides guidance and practice questions for technical interviews.

The twenty-third link is a repeat of the previous link, directing readers to the Lethain article on the hiring funnel.

The twenty-fourth link, once again, takes readers to the Lethain article on performance management systems.

The twenty-fifth link is yet another repeat, leading readers back to the Lethain article on performance management systems.

Words: 940